File storage service system, file management device, file management method, ID denotative NAS server and file reading method

ABSTRACT

The present invention relates to a migration of a file from a path denotative NAS server to an ID denotative NAS server. In a file management device a migration-use path denotative NAS access section obtains a file deposit location from the path denotative NAS server, selects a migration target file based on the deposit location, and sends a read request with the deposit location of the migration target file to the path denotative NAS server, so as to obtain the migration target file. A migration-use denotative NAS access section generates a write request with the migration target file, sends it to the ID denotative NAS servers, and writes the file therein. In addition, the migration-use ID denotative NAS access section registers a GUID received from the ID denotative NAS servers in a file name/GUID management table, together with the file name of the migration target file.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation application of U.S. patent application Ser. No. 12/328,050, filed on Dec. 4, 2008, which is a continuation application of U.S. patent application Ser. No. 10/653,017, filed on Aug. 28, 2003, which claims priority from Japan Patent Application No. 2003-076045, filed on Mar. 19, 2003, all of which are incorporated by reference herein in their entirety.

BACKGROUND OF THE INVENTION

The present invention relates to a file storage service system, comprising a path denotative NAS server and an ID denotative NAS server. In particular, it relates to a technique to allow a file in the path denotative NAS server to migrate into the ID denotative NAS server, and a technique to access a file in the path denotative NAS server from an ID denotative NAS client.

An NAS (Network Attached Storage) system is known as a file storage service system of a client/server type. In the NAS system, when an NAS server receives an access request from an NAS client via a network such as WAN and LAN, the NAS server performs a process according to the requested contents (write/read). In other words, when the NAS server receives from the NAS client a write request with a file the NAS server writes the file into a disk device of its own server and retains the file. When the NAS server receives from the NAS client a read request with a denotation of file, the NAS server reads out the denoted file from the disk device of its own server, and sends the file to the NAS client.

In the meantime, in the aforementioned NAS server, a denotation of a file received from the NAS client is performed based on a deposit location of the file. The deposit location of the file comprises a node name and a file path name, such as “hitachi.co.jp/usr/home/foobar/doc/memo.txt”. Here, “hitachi.co.jp” corresponds to the node name, and “/usr/home/foobar/doc/memo.txt” corresponds to the file path name. Hereinafter, in the present specification the NAS server and the NAS client of a type in which the file denotation is performed based on the file deposit location will be referred to as a path denotative NAS server and a path denotative NAS client. As the path denotative NAS server, there are an NFS (Network File System) server, a CIFS (Common Internet File System) server, or the like. Furthermore, there are documents of prior art describing the path denotative NAS server, “UNIX Internals: The New Frontiers”, authored by Uresh Vahalia, translated by Hideyuki Tokuda, Akira Nakamura, Yoshito Tobe, and Yoshiyuki Tsuda, issued by PEARSON Education, May 2000”, and “NFS illustrated” authored by Brent Callaghan, translated by QUIPU Corporation, issued by ASCII Corporation, Sep. 20, 2001

Recently, a file storage service system, celled as a distributed parallel NAS system, has been suggested. In the distributed parallel NAS system, a file is divided into fragments and they are stored in a plurality of NAS servers in a distributed manner. Therefore, it has been found difficult for the NAS client to perform the file denotation based on the file deposit location, since it is necessary for the NAS client side to grasp all the deposit locations for every fragment. Then, in many of the distributed parallel NAS systems, the NAS server handles the file denotation received from the NAS client, based on a file identifier called as GUID (Global Unique Identifier). When the NAS server receives a write request with a file from the NAS client, the NAS server divides the file into a plurality of fragments, and stores the fragments in a plurality of NAS servers including its own server in a distributed manner. In addition, the NAS server generates a GUID of the file, notifies the NAS client of the GUID thus generated, and manages each of the deposit locations of the fragments in association with the GUID. When the NAS server receives from the NAS client a read request with a denotation of the QUID, the NAS server specifies a plurality of deposit locations being associated with the denoted GUID, restores the file by reading out the fragments respectively from the specified deposit locations, and sends the restored file to the NAS client. As the GUID, for example, a hash value of the file contents is used. The GUID and a method for converting the GUID into file deposit locations are described in “Distributed Content Location for Ubiquitous Environments” authored by Kiyohide Nakauchi, Hiroyuki Morikawa, and Tomonori Aoyama, Technical Report of the Institute of Electronics, Information and Communication Engineers, NS2002-110 IN2002 CS2002, September 2002.

Hereinafter in the present specification, an NAS server and an NAS client of a type in which a file denotation is performed based on the GUID, will be referred to as ID denotative NAS server and ID denotative NAS client. As the ID denotative NAS server, there are “The OceanStore Project” operated by University of California Berkeley Computer Science Division in the U.S. and “PASIS” operated by Carnegie Mellon University in the U.S. As documents of prior art by “The OceanStore Project”, there are “The OceanStore Project Providing Global-Scale Persistent Data”, UC Berkeley Computer Science Division [online] (retrieved on Mar. 1, 2003), Internet <URL: http://oceanstore.cs.berkeley.edu/>, a “Maintenance-Free Global Data Storage” appears in IEEE Internet Computing Vol. 5, No 5 September/October 2001, pp, 40-49, authored by Sean Rhea, Chris Wells, Patrick Eaton Dennis Geels, Ben Zhao, Hakim Weatherspoon, and John Kubiatowicz. As documents of prior art by “PASIS”, there are “PASTS Engineering Survivable Storage”, Carnegie Mellon University [online] [retrieved Mar. 1, 2003] Internet <URL: http://www.pdl.cmu.edu/Pasis/index.html>, and “Survivable information storage systems” IEEE Computer 33(8):61-69, August 2000, authored by Jay J. Wylie, Michael W. Bigrigg, John D. Strunk, Gregory R. Ganger, Han Kiliccote, and Pradeep K. Khosla.

SUMMARY OF THE INVENTION

When an ID denotative NAS server is newly installed in addition to a path denotative NAS server already in operation, a demand from a user is expected that a file managed by the path denotative NAS server accessed from the ID denotative NAS client, by integrating the both servers.

However, as described above, a method of reception of the file denotation from the NAS client different between the ID denotative NAS server and the path denotative NAS server. Therefore, a file within the path denotative NAS server cannot be copied as it is into the ID denotative NAS server. Furthermore, it is not possible for the ID denotative NAS client to access a file in the path denotative NAS server.

The present invention has been made in view of the above situation, and an object of the present invention is to provide a technique to allow a file in the path denotative NAS server to migrate into the ID denotative NAS server. Another object of the present invention is to provide a technique to access a file within the path denotative NAS server from the ID denotative NAS client.

In order to solve the above problems, one aspect of the file storage service system of the present invention comprises a path denotative NAS server which is an NAS server to perform a reception of a file denotation from a client based on a file deposit location, an ID denotative NAS server which is an NAS server to perform the reception of the file denotation from the client based on a file identifier, and a file management device.

Here, the file management device comprises a path denotative NAS access unit which sends a read request with a file deposit location to the path denotative NAS server and reads a file from the path denotative NAS server, an ID denotative NAS access unit which sends a write request with the file obtained by the path denotative NAS access unit to the ID denotative NAS server to writes the file into the ID denotative NAS server, and receives from the ID denotative NAS server a file identifier of the file generated by the ID denotative NAS server, and a file identifier storing unit which stores information relating to the file obtained by the path denotative NS access unit, and the file identifier of the file obtained by the ID denotative NAS access unit in such a manner as associated with each other.

Alternatively, the file management device comprises a path denotative NAS access unit which sends a read request with a file deposit location to the path denotative NAS server and reads a file from the path denotative NAS server, a file identifier generating unit which generates a file identifier of the file obtained by the path denotative NAS access unit, a file identifier registration requesting unit which sends a file identifier registration request with the file deposit location of the file obtained by the path denotative NAS access unit and the file identifier of the file generated by the file identifier generating unit, and registers the file identifier in the ID denotative NAS server in association with the file deposit location, and a file identifier storing unit which stores the in formation relating to the file obtained by the path denotative NAS access unit and the file identifier of the file generated by the file identifier generating unit in such a manner as being associated with each other.

If the file management device corresponds to the latter case, when the file deposit location corresponding to the file identifier received from the client with the read request exists within the path denotative NAS server, the ID denotative NAS server sends the read request with the file deposit location to the path denotative NAS server, reads a file from the path denotative NAS server and sends the file to the client.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic diagram of a file storage service system to which the first embodiment of the present invention is applied.

FIG. 2 is an illustration showing an example registered contents in a GUID/positional information conversion table 25.

FIG. 3 is an illustration showing an example of registered contents in a file name/GUID management table 45.

FIG. 4 is a diagram showing an example of hardware configuration of the file storage Service system as shown in FIG. 1.

FIG. 5 is a flow diagram to explain an operation of file migration of the file management device 4.

FIG. 6 is a schematic diagram of a file storage service system to which the second embodiment of the present invention is applied.

FIG. 7 is a flow diagram to explain an operation of ID registering operation of the file management device 4.

FIG. 8 is a flow diagram to explain a file reading operation of the ID denotative NAS servers 2 ₁, 2 ₂.

FIG. 9 is a schematic diagram of the file storage service system to which the third embodiment of the present invention is applied.

FIG. 10 is a schematic diagram of the file storage service system to which the fourth embodiment of the present invention is applied.

FIG. 11 is a flow diagram to explain an operation (instruction receiving process) of a user terminal 6.

FIG. 12 is an illustration showing an example of a file deposit location tree-structured diagram, which is displayed on the user terminal 6.

FIG. 13 is an illustration showing an example of a file attribute display screen, which is displayed on the user terminal 6.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

Hereafter, preferred embodiments of the present invention will be explained.

Firstly, the first embodiment of the present invention will be explained.

FIG. 1 is a schematic diagram of a file storage service system to which the first embodiment of the present invention is applied. As shown in the FIG. 1, a path denotative NAS server 1, ID denotative NAS servers 2 ₁, 2 ₂, an ID denotative NAS client 3 and a file management device 4 are configured, being connected to each other via a network 5 such as WAN and LAN.

The path denotative NAS server 1 is, as described in Background of the Invention, an NAS server that receives a file denotation from a NAS client, based on a denotation of a file deposit location. As shown in FIG. 1, the path denotative NAS server 1 comprises a network IF (interface) section 11 which connects to the network 5, a storage device IF section 12 which connects to a storage device 15, an access receptor 13 which handles an access request from the path denotative NAS client, and carries out reading/writing of a file from/to the storage device 18, and a positional information management table 14 which registers and manages deposit location information (e.g., a directory structure information) of each file stored in the storage device 18.

When the access receptor 13 receives a request for file deposit location information via the network IF section 11, it reads from the positional information management table 14 the deposit location information of each file stored in the storage device 18, and sends thus readout deposit location information to a sending source of the request for file deposit location information.

When the access receptor 13 receives a write request with a file and a denotation of the file deposit location, via the network IF section 11, it access the storage device 18 via the storage device IF section 12, and writes the file received with the write request to the file deposit location as denoted. Furthermore, the access receptor 13 adds the deposit location information of this file in the positional information management table 14.

When the access receptor 13 receives a read request with a denotation of the file deposit location via the network IF section 11, it accesses the storage device 18 via the storage device IF section 12, and reads out the file stored in the file deposit location as denoted. Then, the access receptor 13 sends via the network IF section 11 the file thus read out, to the sending source of the read request.

The ID denotative NAS servers 2 ₁, 2 ₂ are, as described in Background of the Invention, NAS servers which receive a file denotation from the NAS client based on a denotation of GUID. As shown in FIG. 1, each of those ID denotative NAS servers comprises a network IF section 21 which connects to the network 5, a storage device IF section 22 which connects to the storage device 28 for storing a file, such as HDD, an access receptor 23 which handles an access request from the ID denotative NAS client and reads/writes a file to/from the storage devices 28 of its own server and another ID denotative NAS server a GUID generator 24 which generates a GUID to be given to the file, and a GUID/positional information conversion table 25 which is a table for registering and managing a correspondence between the GUID and the deposit location information of each fragment of the file to which the GUID has been given.

FIG. 2 is an illustration showing an example of registered contents of the GUID/positional information conversion table 25. As shown in FIG. 2, the GUID 251 and the file deposit location 252 of the file, which is given the GUID 251, are associated with each other and registered in the GUID/positional information conversion table 25. The file deposit location 252 comprises a node name (for example, an IP address) 253 for specifying a node, and a file path name 254. In the example as shown in FIG. 1, the node indicates either ID denotative NAS server 2 ₁ or the ID denotative NAS server 2 ₂. The file deposit location 252 is denoted for each of the fragments of the file, being stored in distributed manner. In the example as shown in FIG. 2, the file which is given the QUID “0x00′0000′0000′0000′0000” is divided into four fragments, and it is indicated that those four fragments are stored in distributed manner, respectively with the node names “192.168.0.1” file path name “/dist/0x0000′0000′0000′0000′0000′0000′0001”, node name “192.168.0.1”+file path name “/dist/0x0000′0000′/0000′0000′0000′0000′0002”, node name “192.168.0.2”+file path name “/dist/0x0000′0000′/0000′0000′0000′0000′0003”, node name “192.166.0.2”+file path name “/dist/0x0000′0000′/0000′0000′0000′0000′0004”.

When the access receptor 23 receives a write request with a file via the network IF section 21, it allows the GUID generator 24 to generate a GUID to be given to the file. In addition, the access receptor 23 divides the file into a plurality of fragments, and writes each fragment in the storage device 26 connected to the storage device IF section 22 and/or the storage device 28 connected to another ID denotative NAS server. Then, the access receptor 23 registers the deposit location of each fragment in the GUID/positional information conversion table 25, in association with the GUID, and sends the GUID to the sending source of the write request via the network IF section 21.

When the access receptor 23 of one of the ID denotative NAS servers 2 ₁, 2 ₂ writes a fragment to the storage device 28, which is connected to the other of the ID denotative NAS servers 2 ₁, 2 ₂, access receptor 23 of the one of the ID denotative NAS server 2 ₁, 2 ₂, for example, sends to the other of the ID denotative NAS servers 2 ₁, 2 ₂ in the other end, a write request with a fragment and a denotation of a deposit location of the fragment. In receipt of the write request thus sent, the access receptor 23 of the other of the ID denotative NAS servers 2 ₁, 2 ₂, accesses the storage device 28 connected to its own server and stores in the deposit location thus denoted the fragment received with the write request.

When the access receptor 23 receives a read request with a denotation of a GUID via the network IF section 21, it refers to the GUID/positional information conversion table 25 and specifies a deposit location of each fragment of the file which is given the specified GUID. Then, it accesses the storage device 28 connected to the storage device IF section 22 and/or the storage device 28 connected to another ID denotative NAS server, reads the fragments based on each deposit location thus specified, so as to restore the file, and sends thus restored file to the sending source of the read request.

When the access receptor 23 of one of the ID denotative NAS servers 2 ₁, 2 ₂ reads the fragment from the storage device 28 connected to the other of the ID denotative NAS servers 2 ₁, 2 ₂, the access receptor 23 of the one of the ID denotative NAS server 2 ₁, 2 ₂ sends a read request with a denotation of fragment deposit location to the other of the ID denotative NAS server 2 ₁, 2 ₂. In receipt of this read request, the access receptor 23 of the other of the ID denotative NAS server 2 ₁, 2 ₂ accesses the storage device 20 connected to its own server, reads the fragment the denoted deposit location, and sends the fragment to the one of the ID denotative NAS server 2 ₁, 2 ₂.

The ID denotative NAS client 3 has a function to obtain from the file management device 4 that will be described below, a GUID of a file whose deposit location has migrated from the path denotative NAS server 1 to the ID denotative NAS servers 2 ₁, 2 ₂, in addition to a function as a client of the ID denotative NAS servers 2 ₁, 2 ₂. As shown in FIG. 1, the ID denotative NAS client 3 comprises a network IF section 31 which connects to the network 5, a user IF section 32 which receives an instruction from a user and displays file contents, an ID denotative NAS access section 33 which requests reading/writing of files from/to the ID denotative NAS servers 2 ₁, 2 ₂, and a file management device access section 34 which requests the file management device 4 to provide a GUID.

When the ID denotative NAS access section 33, for example, receives the GUID from a user via the user IF section 32, it generates a read request with the GUID and sends the read request to either of ID denotative NAS servers 2 ₁, 2 ₂, via the network IF section 31. Then, The ID denotative NAS access section 33 receives a file which is given the GUID from either of the ID denotative NAS servers 2 ₁, 2 ₂ and displays the file to user via the user IF section 32.

When the file management access section 34, for example, receives a GUID acquisition instruction from a user via the user IF section 32, it generates a GUID acquisition request and sends the request to the file management device 4 via the network IF section 31. Then, the file management device access section 34 receives from the file management device 4 a GUID of each file having migrated from the path denotative NAS server 1 to the ID denotative NAS servers 2 ₁, 2 ₂, and displays the received GUID to the user via the user IF section 32.

The file management device 4 has a function as a client of the path denotative NAS server 1, as well as a function as a client of the ID denotative NAS servers 2 ₁, 2 ₂, and it allows a file deposit location to migrate from the path denotative NAS server 1 to the ID denotative NAS servers 2 ₁, 2 ₂. In addition, the file management device 4 notifies the ID denotative client 3 of, a QUID of a file, the deposit location of which has migrated from the path denotative NAS server 1 to the ID denotative NAS servers 2 ₁, 2 ₂. As shown in FIG. 1, the file management device 4 comprises a network IF section 41 which connects to the network 5, a user IF section 42 which receives an instruction from a user, a migration-use path denotative NAS access section 43 which requests the path denotative NAS server 1 to retrieve and read out a file, a migration-use ID denotative NAS access section 44 which requests the ID denotative NAS servers 2 ₁, 2 ₂ to write a file, a file name/GUID management table 45 which registers and manages a correspondence between a file name and a GUID of the file, and a client request receptor 46 which notifies the ID denotative client 3 of the registered contents of the file name/GUID management table 45, according to the Milt) acquisition request from the ID denotative client 3.

FIG. 3 is an illustration showing an example of registered contents of the file name/GUID management table 45. As illustrated, a file name 451 of a file and a GUID 452 given to the file, are registered in the file name/GUID management table 45, in such a manner as associated with each other. The example as shown in FIG. 3 indicates that the GUID of a file with the file name “proceeding_vol1_no1” is “0x00′0000′0000′0000′0000”, and the GUID of a file with the file name “memo” is “0x00′0000′0000′1111′0000”.

FIG. 4 is a diagram showing an example of hardware configuration of the file storage service system as indicated in FIG. 1. As shown in FIG. 4, a functional configuration of the path denotative NAS server 1 as shown in FIG. 1 is implemented by allowing a CU 71 to execute a predetermined program (a program for the path denotative NAS server) stored in a memory 72, in a computer system comprising the CPU 71, the memory 72, an NIC (Network Interface Card) 73 which connects to the network 5, an HBA (Host Bus Adapter) 74 which connects to the storage device 18, and a bus 75 which connects each of those devices. In this implementation, the memory 72 is used for the positional information management table 14. A functional configuration of the ID denotative NAS servers 2 ₁, 2 ₂ as shown in FIG. 1 is implemented by allowing a CPU 71 to execute a predetermined program (a program for the ID denotative NAS server) stored in a memory 72 in a computer system having a similar configuration as that of the path denotative NAS server 1. In this implementation, the memory 72 is used for the GUID/positional information conversion table 25.

A functional configuration of the ID denotative NAS client 3 as shown in FIG. 1 is implemented by allowing a CPU 71 to execute a predetermined program (a program for the ID denotative NAS client and a program for accessing the file management device) stored in a memory 72, in a computer system comprising the CPU 71 the memory 72, an NIC 73, an I/O device 76 such as a display and a keyboard, and a bus 75 which connects those devices above. A functional configuration of the file management device 4 as shown in FIG. 1 is implemented by allowing a CPU 71 to execute a predetermined program (a program for the file management device) stored in a memory 72, in a computer system having a similar configuration as that of the ID denotative NAS client 3. In this implementation, a memory 72 is used for the file name/GUID management table 45.

next, in the file, storage service system with the above configuration, an operation for the file management device 4 to migrate a file within the path denotative NAS server 1 to migrate into the ID denotative NAS servers 2 ₁, 2 ₂, (referred to as a file migrating operation.) will be explained. Hereinafter, this operation will be referred to as a file migrating operation. FIG. 5 is a flow diagram for explaining the file migrating operation of the file management device 4. This flow starts when the user IF section 42 receives a file migrating instruction from a user.

firstly, the migration-use path denotative NAS access section 43 generates a request for file deposit location information, and sends it to the path denotative NAS server 1 via the network IF section 41. Then, the migration-use path denotative NAS access section 43 obtains from the path denotative NAS server 1, deposit location information of each file within the path denotative NAS server 1 (S1001).

Subsequently, the migration-use path denotative NAS access section 43 selects a migration target file, out of the files within the path denotative server 1 which are specified based on the deposit location information obtained from the path denotative NAS server 1. Then, the migration-use path denotative NAS access section 43 generates a read request with the deposit location information of the selected file, sends the read request to the path denotative NAS server 1 via the network IF section 41, and obtains the migration target file from the path denotative NAS server 1 (S1002). Then, the migration-use path denotative NAS access section 43 passes the migration target file to a migration-use ID denotative NAS access section 44.

Subsequently, the migration-use ID denotative NAS access section 44 adds a new record to the file name/GUID management table 45, and registers a file name of the migration target file on the added record (S1003). The file name of the migration target file can be specified, based on the deposit location information of the migration target file, file attribute information added onto the migration target file itself and the like.

Subsequently, the migration-use ID denotative NAS access section 44 generates a write request with the migration target file, sends the write request to either of the ID denotative NAS servers 2 ₁, 2 ₂ and obtains a GUID given to the migration target file from the either of the ID denotative NAS servers 2 ₁, 2 ₂ (S1004).

Subsequently, the migration-use ID denotative NAS access section 44 registers the GUID of the migration target file which is obtained in step S1004, on the record which is added to the file name/GUID management table 45 in step S1003 (S1005). Then, the migration-use ID denotative NAS access section 44 notifies the migration-use path denotative NAS access section 43 of a completion of the migrating process as to the migration target file.

When the migration-use path denotative NAS access section 43 receives the notification of the completion of the migrating process as to the migration target file from the migration-use ID denotative NAS access section 44, it is determined whether or not all the files within the path denotative NAS server 1, which are specified by the deposit location information obtained from the path denotative NAS server 1, are selected as migration target files (S1006). If there is a file which is not selected, a process returns to S1002 to select the file as a migration target file, then, the process continues. Alternatively, if all the files within the path denotative NAS server 1 are selected as migration target files, this flow is ended.

According to the process above, all the files within the path denotative NAS server 1 are stored in the ID denotative NAS servers 2 ₁, 2 ₂, and GUIDs of these files are registered in the file name/GUID management table 45 of the file management device 4. As described above, the client request receptor 46 notifies the ID denotative client 3 of the registered contents of the file name/GUID management table 45, according to the GUID acquisition request from the ID denotative client 3. Then, the ID denotative client 3 sends a read request with the GUID thus obtained to the ID denotative NAS servers 2 ₁, 2 ₂, whereby the ID denotative client 3 can read a file having migrated from the path denotative NAS server 1 to the ID denotative NAS servers 2 ₁, 2 ₂. According to the present embodiment of the invention, it is possible to perform a smooth migration of the files within the path denotative NAS server 1 to the ID denotative NAS servers 2 ₁, 2 ₂.

In the present embodiment of the invention, a function of the file management device 4 may be held by the path denotative NAS server. In other words, in FIG. 4, the program for the file management device and the file name/GUID management table stored in the memory 72 of the file management device 4 may be stored in the memory 72 of the path denotative NAS server 1, and the CPU 71 of the path denotative NAS server 1 may execute the programs for the file management device 4, so that the path denotative NAS server 1 may carry out the processes that is supposed to be executed by the file management device 4. In this case, it is unnecessary to separately provide the file management device 4 from the path denotative NAS server.

Next, the second embodiment of the present invention will be explained.

In the first embodiment above, a file itself within the path denotative NAS server 1 is written in the ID denotative NAS servers 2 ₁, 2 ₂, whereby the ID denotative client 3 can access the file. Alternatively, in the second embodiment, the ID denotative client 3 can access the file without writing the file itself within the path denotative NAS server 1 to the ID denotative NAS servers 2 ₁, 2 ₂.

FIG. 6 is a schematic diagram of the file storage service system, to which the second embodiment of the present invention has been applied. As shown in FIG. 6, each of the devices comprising the file storage service system of the second embodiment is similar to those of the first embodiment as shown in FIG. 1. However, a part of the functional configuration of the ID denotative NAS servers 2 ₁, 2 ₂, and the file management device 4 is different from that of the first embodiment. As for the hardware configuration of each device comprising the file storage service system of the second embodiment is similar to that of the first embodiment as shown in FIG. 4.

The ID denotative NAS servers 2 ₁, 2 ₂ of the second embodiment are different from the ID denotative NAS server 2 ₁, 2 ₂ of the first embodiment in the point that an access receptor 23 a is provided instead of the access receptor 23. The access receptor 23 a performs the following processing in addition to the function of the access receptor 23 of the first embodiment.

That is, when the access receptor 23 a receives from the file management device 4 via the network IF section 21 a GUID registering request with a GUID and file deposit location information, the access receptor 23 a adds a new record to the GUID/positional information conversion table 25, and registers in this record, the GUID and file deposit location information (node name+file path name) received with the GUID registering request.

Further, the access receptor 23 a also has a function as a path denotative NAS client. When the file deposit location information registered in the GUID/positional information conversion table 25 in association with the GUID received with the read request from the ID denotative NAS client 3, has a node name indicating the path denotative NAS server 1, it generates a read request with this file deposit location information, and sends the read request to the path denotative NAS server 1. Then, the access receptor 23 a sends the file obtained from the path denotative NAS server 1, to the ID denotative NAS client 3.

The file management device 4 of the present embodiment is different from the file management device 4 of the first embodiment in the points that a migration-use path denotative NAS access section 43 a and ID migration-use ID denotative NAS access section 44 a are provided instead of the migration-use path denotative NAS access section 43 and the migration-use ID denotative NAS access section 44, and that a QUID generator 47 for generating a GUID is newly provided.

The migration-use path denotative NAS access section 43 a passes a file read out from the path denotative NAS server 1, together with the deposit location of the file in the path denotative NAS server 1, to the ID migration-use ID denotative NAS access section 44 a.

The ID migration-use ID denotative NAS access section 44 a allows the GUID generator 47 to generate a GUID of the file which is received from the migration-use path denotative NAS access section 43 a. Then, the ID migration-use ID denotative NAS access section 44 a registers the GUID generated by the GUID generator 47 in the file name/GUID management table 45, together with a file name of the file received from the migration-use path denotative NAS access section 43 a. In addition, the ID migration-use ID denotative NAS access section 44 a generates a GUID registering request with the GUID generated by the GUID generator 47 and the file deposit location information received from the migration-use path denotative NAS access section 43 a, and sends the GUID registering request to either of the ID denotative NAS servers 2 ₁, 2 ₂, via the network IF section 41.

Subsequently, in the file storage service system with the above configuration, an operation for the ID denotative client 3 to be able to access a file within the path denotative NAS server 1, without writing the file itself into the ID denotative NAS servers 2, by the file management device 4 (referred to as ID registering operation) will be explained. FIG. 7 is a flow diagram to explain the ID registering operation of the file management device 4. This flow starts when the user IF section 42 receives an ID registering instruction from a user.

Firstly, the migration-use path denotative NAS access section 43 a obtains deposit location information of each file within the path denotative NAS server 1 in a similar manner as explained insteps S1001 and S1002 of FIG. 5 (S2001). And the migration-use path denotative NAS access section 43 a selects a migration target file among of the files within the path denotative NAS server 1, the files being specified based on the obtained deposit location information. Then, the migration-use path denotative NAS access section 43 a sends a read request with the deposit location information of the selected file to the path denotative NAS server 1, and obtains the migration target file from the path denotative NAS server 1 (S2002). Further, the migration-use path denotative NAS access section 43 a passes the migration target file and the deposit location information of the migration target file within the path denotative NAS server 1 to the ID migration-use ID denotative NAS access section 44 a.

Subsequently, the ID migration-use ID denotative NAS access section 44 a allows the GUID generator 47 to generate a GUID of the migration target file (S2003). Then, it adds a new record to the file name/GUID management table 45, and registers a file name of the migration target file and the GUID generated by the GUID generator 41 (S2004).

Subsequently, the ID migration-use ID denotative NAS access section 44 a generates a QUID registering request with the GUID of the migration target file and the file deposit location information, and sends the GUI registering request to either of the ID denotative NAS servers 2 ₁, 2 ₂ (S2005). As described above, in the ID denotative NAS servers 2 ₁, 2 ₂, either of which received the GUID registering request, the access receptor 23 a adds a new record to the GUID/positional information conversion table 25, and registers in this record the GUID and the deposit location information (node name+file path name), received with the GUID registering request.

Subsequently, the ID migration-use ID denotative NAS access section 44 a notifies the migration-use path denotative NAS access section 43 a of a completion of the ID registering process as to the migration target file. When the migration-use path denotative NAS access section 43 a receives from the ID migration-use ID denotative NAS access section 44 a, the notification of the completion of the ID registering process as to the migration target file, it determines whether or not all the files within the path denotative NAS server 1, which are specified by the deposit location information obtained from the path denotative NAS server 1, are selected as migration target files (S2006). If there is a file not selected, the process returns to S2002 to select the file as a migration target file, then, the process continues. Alternatively, if all the files within the path denotative NAS server 1 are selected as migration target files, the flow is ended.

According to the process above, GUIDs of all the files within the path denotative NAS server 1 together with the file deposit location information therein, are registered in the GUID/positional information conversion table 25 of the ID denotative NAS servers 2 ₁, 2 ₂. Further, these GUIDs are registered in the file name/GUID management table 45 of the file management device 4. As described above, the client request receptor 46 notifies the ID denotative client 3 of the registered contents of the file name/GUID management table 45 according to the GUID acquisition request from the ID denotative client 3. Then, the ID denotative client 3 can read out a file within the path denotative NAS server 1, by sending to the ID denotative NAS servers 2 ₁, 2 ₂, a read request with the GUID obtained from the file management device 4.

Subsequently, in the file storage service system as configured above, a file reading operation of the ID denotative NAS servers 2 ₁, 2 ₂ will be explained. FIG. 8 is a flow diagram to explain the file reading operation of the ID denotative NAS servers 2 ₁, 2 ₂. This flow starts when the access receptor 23 a receives a read request with a GUID, from the ID denotative client 3 via the network IF section 21.

Firstly, the access receptor 23 a obtains deposit location information corresponding to the GUID received with the read request, by use of the GUID/positional information conversion table 25 (S3001). Here, if the GUID received with the read request is not registered in the GUID/positional information conversion table 25 provided in its own server, the access receptor 23 a makes an inquiry to another ID denotative NAS servers 2 ₁, 2 ₂, and obtains the deposit location information corresponding to the GUID received with the read request, from the another ID denotative NAS servers 2 ₁, 2 ₂.

Subsequently, the access receptor 23 a determines whether or not a node name included in the obtained deposit location information (node name+file path name) indicates the path denotative NAS server 1 (S3002). If the node name included in the deposit location information does not indicate the path denotative NAS server 1, that is, the node name indicates the ID denotative NAS servers 2 ₁, 2 ₂, a normal operation as an ID denotative NAS server is performed. And the access receptor 23 a restores a file by obtaining fragments respectively from the fragment deposit locations, which are specified by the deposit location information (S3003). Whereby, the access receptor 23 a obtains the file.

Alternatively, if the node name included in the deposit location information indicates the path denotative NAS server 1, the access receptor 23 a generates a read request with this deposit location information, and sends the read request to the path denotative NAS server 1 via the network IF section 21 (S3004). Then, the access receptor 23 a obtains the file from the path denotative NAS server 1 (S3005).

With the flow above, when the access receptor 23 a obtains the file given the GUID received with the read request, it sends the file via the network ID section 21 to the ID denotative NAS client 3 which is a sending source of the read request (S3006).

As described above, according to the present embodiment, it is possible to access a file within the path denotative NAS server 1 from the ID denotative NAS client 3.

Next, the third embodiment of the present invention will be explained.

In the first embodiment as described above, the file itself within the path denotative NAS server 1 is written in the ID denotative NAS servers 2 ₁, 2 ₂, whereby the ID denotative client 3 can access the file. In the second embodiment above, the ID denotative client 3 can access the file without writing the file itself within the path denotative NAS server 1 into the ID denotative NAS servers 2 ₁, 2 ₂. On the other hand, the third embodiment is made to handle the both cases, i.e., the ID denotative client 3 can access the file by writing the file itself within the path denotative NAS server 1 into the ID denotative NAS servers 2 ₁, 2 ₂ (the first embodiment), and the ID denotative client 3 can access the file without writing the file itself within the path denotative NAS server 1 into the ID denotative NAS servers 2 ₁, 2 ₂ (the second embodiment).

FIG. 9 is a schematic diagram, of the file storage service system to which the third embodiment of the present invention is applied. As shown in FIG. 9, each of the devices comprising the file storage service system of the third embodiment is similar to those of the first embodiment as shown in FIG. 1. However, a part of the functional configuration of the ID denotative NAS servers 2 ₁, 2 ₂ and the file management device 4 is different. As for the hardware configuration of each of the devices comprising the file storage service system of the third embodiment, it is similar to that of the first embodiment as shown in FIG. 4.

The ID denotative NAS servers 2 ₁, 2 ₂ of the third embodiment are different from those in the first embodiment in the point that an access receptor 23 b is provided instead of the access receptor 23. The access receptor 23 b performs the following process in addition to the functions of the access receptor 23 of the first embodiment and the access receptor 23 a of the second embodiment.

In other words, when the access receptor 23 b receives a GUID deletion request with the GUID front the file management device 4 via the network IF section 21, the access receptor 23 b deletes the record with the QUID from the GUID/positional information conversion table 25.

The file management device 4 of the third embodiment is different from that of the first embodiment in the point that a migration-use path denotative NAS access section 43 b, a migration-use ID denotative NAS access section 44 b are provided instead of the migration-use path denotative NAS access section 43 and the migration-use ID denotative NAS access section 44, and the point that the ID migration-use ID denotative NAS access section 44 a and the GUID generator 47 are newly provided, which are provided, in the file management device 4 of the second embodiment.

In the file storage service system with the configuration above, an ID registering operation of the file management device 4 is similar to that of the second embodiment as shown in FIG. 7. In addition, a file migrating operation of the file management device 4 is similar to that of the first embodiment as shown in FIG. 5, except the following points. That is, preceding the execution of S1001 the file management device 4 generates a GUID deleting request with each GUID registered in the file name/GUID management table 45 and sends the GUID deleting request to each of the ID denotative NAS servers 2 ₁, 2 ₂ via the network IF section 41. The GUIDs registered by the ID registering operation are respectively deleted from the GUID/positional information conversion tables of the ID denotative NAS servers 2 ₁, 2 ₂. As well as a record having each GUID which is requested to delete, is deleted from the file name/GUID management table 45. Then, the flow as shown in FIG. 5 is executed.

In general, the file migrating operation is accompanied with a file forwarding process from the file management device 4 to the ID denotative NAS servers 2 ₁, 2 ₂ and a file writing process in the ID denotative NAS servers 2 ₁, 2 ₂. Therefore, the file migrating operation takes a longer period of time than the ID registering operation. According to the third embodiment, since the file management device 4 performs the ID registering operation before the file migrating operation, the ID denotative NAS client 3 can access a file, even before the completion of the file migrating operation as far as the ID registering operation is completed.

Next, the fourth embodiment of the present invention will be explained.

FIG. 10 is a schematic diagram of the file storage service system to which the fourth embodiment of the present invention is applied. As shown in FIG. 10, the file storage service system of the fourth embodiment has a configuration that a user terminal 6 is added to the file storage service system of the third embodiment as shown in FIG. 9

The user terminal 6 comprises a network IF section 61, a user IF section 62, a file view generator 63 and an instruction generating section 64.

The file view generator 63 generates a file view screen for receiving designation of a migration target file of the ID registering operation or the file migrating operation, by use of file deposit location information registered in the positional information management table 14 of the path denotative NAS server 1, file attribute information (file name, creation date and time, file creator, file update person, file size and the like), which is given to the file itself stored in the storage device 18 of the path denotative NAS server 1, and a QUID registered in the file name/GUID management table 45 of the file management device 4, and the like. Then, the file view generator 63 displays thus generated file view screen on a display via the user IF section 62.

The instruction generating unit 64 generates an ID registering instruction or a file migrating instruction, with deposit location information of the designated migration target file, according to the instruction received from the user via the user IF section 62, and sends the instruction to the file management device 4 via the network IF section 61.

The user terminal 6 as described above can also be implemented by allowing the CPU to execute a predetermined program stored in the memory in a computer system having a similar configuration as that of the ID denotative client 3

FIG. 11 is a flow diagram to explain an operation (instruction receiving process) of the user terminal 6. This flow starts when the user IF section 62 receives from a user an instruction for displaying a file view.

Firstly, the file view generator 63 generates a file deposit location information request, and sends the request to the path denotative NAS server 1 via the network IF section 61. Then, the file view generator 63 obtains from the path denotative NAS server 1, the deposit location information of each file within the path denotative NAS server 1 (S4001).

Subsequently, the file view generator 63 generates a file attribute information request with the deposit location information of each file obtained in step S4001, and sends the request to the path denotative NAS server 1 via the network IF section 61. In the path denotative NAS server 1, when the access receptor 13 receives the file attribute information request, it accesses the file deposit location given the file attribute information request via the storage device IF section 12, for example, and obtains the file attribute information held by the file itself, which is registered at the deposit location. Alternatively, it obtains the file attribute information from the file attribute management table which is not illustrated, where the file attribute information is registered in association with the deposit location. Then, the access receptor 13 sends the file attribute information thus obtained to the user terminal 6 via the network IF section 11. The file view generator 63 obtains this file attribute information via the network IF section 61 (S4002).

Subsequently, the file view generator 63 generates a GUID acquisition request and sends the request to the file management device 4 via the network IF section 61. Then, the file view generator obtains each GUID registered in the filename/GUID management table 45, together with the file name, from the file management device 4 (S4003).

Then, the file view generator 63 generates a deposit location tree-structured diagram (directory structure) within the path denotative NAS server 1, based on the file deposit location information of each file obtained in step S4001, and displays the structure on the display via the user IF section 62 (S4004). FIG. 12 shows an example of the file deposit location tree-structured diagram displayed on the user terminal 6. In this example, it is indicated that four files, “proceeding_vol1_no1”, “memo”, “find”, and “who” are stored within the path denotative NAS server 1, and two files “proceeding_vol1_no1” and “memo” are stored in a deposit location (directory) “/home/abc_committee/doc/”, and two other files “find” and “who” are stored in another deposit location (directory), “/usr/bin/”. A check box 622 is provided to each file, and the user manipulates a cursor 621 to enter a check in a desired check box 622, so that a file can be selected to display the file attribute information.

When the file view generator 63 receives from the user via the user IF section 62, a file designation as to any of the files displayed in the file deposit location tree-structured diagram (S4005), it specifies file attribute information of the designated file, out of the file attribute information obtained in step S4002. Then, the file view generator 63 generates a file attribute display screen for presenting the user the specified file attribute information, and shows it via the user IF section 62 on the display (S4006). Here, if the GUID corresponding to the file name of the designated file is included in the GUIDs obtained in step S4003, the GUID corresponding to the file name of the designated file is also included in the file attribute display screen. FIG. 13 shows an example of the file attribute display screen displayed on the user terminal 6. In this example, the GUID of the file is displayed together with the file attribute information, therefore, this file is accessible from the ID denotative NAS client 3. In FIG. 13, the reference number 623 indicates a button to receive an instruction for returning to a screen of the file deposit location tree-structured diagram on the display. The reference number 624 indicates a button to receive an instruction for allowing the file management device 4 to carry out an ID registering operation as to the displayed file, and the reference number 625 is a button to receive an instruction for allowing the file management device 4 to carry out a file migrating operation as to the displayed file. The user manipulates the cursor 621 to select a desired button out of the buttons 623 to 625.

When the user IF section 62 receives an instruction from a user to display the file deposit location tree-structured diagram (“No” in step S4007, and “Yes” in step S4008), the user IF section 62 notifies the file view generator 63 of this instruction. In receipt of this instruction, the file view generator 63 displays the file deposit location tree-structured diagram on the display by returning to step S4004. In addition, when the user IF section 62 receives an instruction to allow the file management device 4 to carry out the ID registering operation or to carry out the file migrating operation as to the file displayed in the file attribute display screen (“Yes” in step S4007), the user IF section 62 notifies the instruction generating section 64 of this instruction. In receipt of this instruction, the instruction generating section 64 generates an ID registering instruction or a file migrating instruction, together with the file name and the file deposit location of the file displayed in the file attribute display screen, and sends the instruction to the file management device 4 via the network IF section 61 (S4009).

In the file management device 4 when the migration-use path denotative NAS access section 43 b receives from the user terminal 6 the ID registering instruction with the file name and the file deposit location, it deletes a record including the file name from the file name/GUID management table 45. Then, a file specified by this file name and the file deposit location is considered as emigration target file, and steps from S2002 to S2905 as shown in FIG. 7 are executed.

On the other hand, in the file management device 4, when the migration-use path denotative NAS access section 43 b receives from the user terminal the file migrating instruction with the file name and the file deposit location, it specifies a GUID corresponding to the file name from the file name/GUID management table 45. Then, the migration-use path denotative NAS access section 43 b generates a GUID deletion request with thus specified GUID, sends the request to each of the ID denotative NAS servers 2 ₁, 2 ₂ via the network IF section 41, and deletes the GUID thus specified respectively from the GUID/positional information conversion tables 25 of the ID denotative servers 2 ₁, 2 ₂. And, the migration-use path denotative NAS access section 43 b deletes a record of thus specified GUID from the file name/GUID management table 45. Then, considering the file specified by the file name and the file deposit location, as a migration target file, the steps from S1002 to S1005 as shown in FIG. 5 are executed.

According to the above embodiment, it is possible to carry out individually, the ID registering operation and the file migrating operation as to a file within the path denotative NAS server 1, which is designated by a user via the user terminal 6. In other words, the user can selectively conduct a file migration, considering extinguish of the path denotative NAS server 1, and a free space of the ID denotative NAS servers 2 ₁, 2 ₂.

The present invention is not limited to each embodiment as described above, and various changes and modifications may be possible within the scope of the invention. For example, in each of the above embodiments, the number of devices comprising the file storage service system is not necessarily limited to the number as shown in the figures. In addition, in each of the above embodiments, the file management device 4 and the ID denotative NAS client 3 may be configured to be on one computer system. In addition, in each of the above embodiments, another file identifier may be used instead of the GUID. In the fourth embodiment, the file management device 4, the ID denotative NAS client 3 and the user terminal 6 may be configured on one computer system. Furthermore, the user terminal 6 of the fourth embodiment may be provided in the file storage service system of the first embodiment or the second embodiment.

As described above, according to the present invention, it is possible to allow a file within the path denotative NAS server to migrate into the ID denotative NAS server. In addition, it is also possible for the ID denotative NAS client to access the file within the path denotative NAS server. 

What is claimed is:
 1. A system comprising: a first file server configured to manage a plurality of files and be dedicated to receive an access request with a path which designates one of the files therein, a second file server configured to manage a plurality of files and dedicated to receive an access request with a global identifier independent of file location which designates one of the files therein, the second file server being coupled to the first file server and a client, a file management device for migrating the files in the first file server to the second file server, the file management device being coupled to the first and the second file server, and the client, wherein, the file management device is configured to, in advance of the migration, obtain paths of the files in the first file server, generate a global identifier for each of the files in the first file server, send registration requests with the generated global identifiers and to obtain locations of the files in the first file server to the second file server, and send the generated global identifiers to the client, wherein, the second file server is configured to, in response to the registration request, store information which indicates corresponding relationship between each of the global identifiers and each of the paths of the files in the first file server, wherein, the client is configured to, send a read request with the global identifier obtained by the first file server, and wherein the client is configured to read a file having migrated from a path of the first file server to the second file server, wherein, the second file server is configured to, in response to the read request with a global identifier from the client, determine whether a file designated by the global identifier exists in the first file server or the second file server based on the information, and if the designated file exists in the first file server, obtain a path corresponding to the designated global identifier from the information, send a read request with the corresponding paths to the first file server, and send the received file to the client.
 2. The system according to claim 1, wherein, the second file server is configured to, if the designated file exists in the second file server, read the designated file therein, and send the read file to the client.
 3. The system according to claim 1, wherein, the file management device is configured to, when migrating one of the files in the first file server to the second file server, send a delete request with one of the generated global identifier corresponding to the file to be migrated to the second file server, wherein, the second file server is configured to, in response to the delete request, delete the received global identifier and corresponding location from the information.
 4. The system according to claim 1, wherein the file management device is configured to send a read request with one of the obtained locations to the first file server, receive the file designated by the location, and send a write request with the received file to the second file server after sending the delete request, wherein, the second file server is configured to, in response to the write request from the file management device, generate a global identifier of the received file, and store information which indicates corresponding relationship between the generated global identifier and location of the received file. 